Skip to content

feat: forward reqwest's rustls-no-provider feature#556

Merged
64bit merged 2 commits into
64bit:mainfrom
valkum:feat/rustls-no-provider
May 21, 2026
Merged

feat: forward reqwest's rustls-no-provider feature#556
64bit merged 2 commits into
64bit:mainfrom
valkum:feat/rustls-no-provider

Conversation

@valkum
Copy link
Copy Markdown
Contributor

@valkum valkum commented May 21, 2026

This closes #547

This adds a new feature rustls-no-provider which will forward to reqwest. This allows users to provide their own rustls crypto provider.

This contains additions to the CI jobs to prevent regressions in the future.

valkum added 2 commits May 21, 2026 15:15
Exposes reqwest 0.13's `rustls-no-provider` feature so consumers can
opt out of the bundled `aws-lc-rs` crypto provider and install their
own (e.g. `ring`).
Adds a `tls-features` job that builds each TLS variant against
chat-completion (`rustls`, `rustls-no-provider`, `native-tls`,
`native-tls-vendored`) and asserts via `cargo tree` that:

- `rustls-no-provider` does NOT pull in `aws-lc-rs` (the regression
  we want to protect against).
- `rustls` DOES pull in `aws-lc-rs` (sanity check that the assertion
  above is meaningful).
Copy link
Copy Markdown
Owner

@64bit 64bit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this, love it! 🎉

@64bit 64bit merged commit 1745127 into 64bit:main May 21, 2026
103 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow reqwest 0.13's rustls-no-provider feature

2 participants